home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20000824-20010305
/
000125_news@columbia.edu _Fri Dec 1 17:41:29 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
4KB
Return-Path: <news@columbia.edu>
Received: from watsun.cc.columbia.edu (watsun.cc.columbia.edu [128.59.39.2])
by uhaligani.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id RAA12824
for <kermit.misc@cpunix.cc.columbia.edu>; Fri, 1 Dec 2000 17:41:29 -0500 (EST)
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id RAA26980
for <kermit.misc@watsun.cc.columbia.edu>; Fri, 1 Dec 2000 17:41:28 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id RAA25685
for kermit.misc@watsun.cc.columbia.edu; Fri, 1 Dec 2000 17:33:01 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: jrd@cc.usu.edu (Joe Doupnik)
Subject: Re: Ms-kermit and Windows 9x/NT
Message-ID: <97pEN0dbn83W@cc.usu.edu>
Date: 1 Dec 00 15:11:35 MDT
Organization: Utah State University
To: kermit.misc@columbia.edu
In article <908ju7$9r4$1@newsmaster.cc.columbia.edu>, jaltman@watsun.cc.columbia.edu (Jeffrey Altman) writes:
> In article <sGAA1yRokSWH@cc.usu.edu>, Joe Doupnik <jrd@cc.usu.edu> wrote:
> : In article <908ca2$8qd$1@wanadoo.fr>, "GILBERT SA" <gilbert.sa@wanadoo.fr> writes:
> : > Please , excuse me for my English (I am French !)
> : >
> : > I use only 2 functions of KERMIT (GET and SEND for the transfer file ASCII
> : > on serial port RS232 between a PC (COM1) and an industrial material).
> : > I don't want to use K95 for prices problems.
> : > I should use MSkermit 3.14 or 3.15 for MS-DOS only.
> : > But, the PC work with Windows 32 bits (98 or NT).
> : >
> : > Sometimes, some PC, I have error '' Unknown hardware for port, using BIOS .'
> : > '
> : >
> : > In " MSkermi.ini " I impose :
> : > Set com1 \x03f8 4
> : > Set port com1
> : > But it does not change.
> : >
> : > Please , have you a solution (not by using K95 !)
> : >
> : > Thank you
> : > Sincerely
> : >
> : > Philippe R
> : -------
> : Windows thinks it owns the serial port hardware (insert the usual
> : MS jokes here). There is an easy way to avoid that, by not starting the
> : GUI. See MS docs on hidden text file msdos.sys to include line bootgui=0.
> : Nevertheless, Windows tries to present a simulated serial port to MSK.
> : If that port is consumed by some Windows app then things won't work and
> : you will see that Unknown hardware message.
> : Joe D.
>
>
> Obviously, there is no way to avoid starting the GUI on NT/2000. And
> as of the release of Windows ME this option has been taken away as well.
>
Not really. The GUI need not start for any of these operating
systems, directives from MS not withstanding. The multiple boot capabilities
in them permit booting to a variety of final states, and I do just that.
See msdos.sys for Win9x. For NT use its boot loader to not start NT but
start another o/s instead. However, I do not have Windows ME and thus
cannot state its behavior with certainty.
> The issue about the port numbers and interrupt values is most likely
> caused by Windows' use of Plug N Play which assigns random values each
> time the machine starts. The only way to use these devices in a
> consistent manner is to use a Windows device name. K95 can do that.
> MS-DOS Kermit cannot.
I have never heard of a case where Windows relabels serial port
Port and/or IRQ values. The serial ports are not Plug and Play PCI devices,
they are ISA bus devices (Southbridge for PCI modern chipset folks, legacy
devices for marketing people).
Competition for the serial port is the likely cause of trouble, as
is competition amongst other devices for those resources. Moving the port
values to non-standard ones via the Bios is also a possibility.
Joe D.
> Jeffrey Altman * Sr.Software Designer
> The Kermit Project * Columbia University
> 612 West 115th St * New York, NY * 10025 * USA
> http://www.kermit-project.org/ * kermit-support@kermit-project.org